Skip to content

Set User-Agent on outbound HTTP requests#55

Merged
andrew merged 1 commit intomainfrom
user-agent
Apr 13, 2026
Merged

Set User-Agent on outbound HTTP requests#55
andrew merged 1 commit intomainfrom
user-agent

Conversation

@andrew
Copy link
Copy Markdown
Contributor

@andrew andrew commented Apr 13, 2026

Closes #31.

Requests now identify themselves as forge/<version> instead of Go-http-client/2.0. The version comes from the same ldflags-injected cli.Version that forge version prints, so release builds get forge/0.4.0 and dev builds get forge/dev.

The header is set by a RoundTripper in internal/resolve that wraps http.DefaultTransport. It clones the request before mutating headers and leaves any explicitly-set User-Agent alone, so forge api -H "User-Agent: something" still works as an override. The transport is wired into all four forge SDK clients via resolve.newClient and into the raw forge api path which previously used http.DefaultClient directly.

@andrew andrew merged commit 0fe34f9 into main Apr 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

user-agent for forge requests

1 participant